Computerized systems and methods for generating and modifying data for module implementation

ABSTRACT

The present disclosure may be directed to a system for generating and modifying data for modules. The system may include receiving, from a user via a proxy server, a request and user information associated with the user; based on the determination that the request comprises a test, calling a mobile application programming interface. The mobile application programming interface may be configured to perform steps including retrieving data; performing the test on the module using the retrieved data; performing a verification on responses from the test to predetermined responses; and sending results of the performed verification to the user. The system may include implementing the module based on the performed verification.

TECHNICAL FIELD

The present disclosure generally relates to computerized systems andmethods for generating and modifying data for modules. In particular,embodiments of the present disclosure relate to inventive andunconventional systems related to using a proxy server and calling amobile application programming interface to perform tests on modules andto implement modules.

BACKGROUND

Module implementation by developers often relies on testing modules inorder to successfully deploy and manage new and existing modules. Whenmodules are not tested, the intended behavior of the module may not bepreserved. Module tests include controls that are critical to preservingthe intended behavior of a module, especially when the module ismodified or when new modules are implemented.

Module testing often involves the use of static test data. However, theuse of static test data does not result in effective module testing forevery module. For example, testing modules that depend on time-sensitivefactors (e.g., dates) using static test data may not produce realisticresults. For these modules, dynamic (e.g., real-time) or mock test datamay produce more realistic results. For other modules, static test datamay produce more realistic results. In some cases, modules may need tobe implemented without testing.

The quality of an organization's online platform and, consequently, theexperiences of users are severely reduced when the online platformincludes faulty modules that have not been tested properly or when theimplementation of modules that do not require testing is delayed due tomodule testing. The quality of an organization's online platform wouldbe significantly improved if the online platform automaticallydetermined which modules required testing and which modules could beimplemented accordingly.

Therefore, there is a need for improved systems and methods forperforming tests on modules and implementing modules.

SUMMARY

One aspect of the present disclosure is directed to a system forgenerating and modifying data for modules. The system may include amemory storing instructions and at least one processor configured toexecute the instructions to receive, from a user via a proxy server, arequest and user information associated with the user; based on thedetermination that the request comprises a test, call a mobileapplication programming interface. The mobile application programminginterface may be configured to perform steps including retrieving data;performing the test on the module using the retrieved data; performing averification on responses from the test to predetermined responses; andsending results of the performed verification to the user. The systeminstructions may include implementing the module based on the performedverification.

Another aspect of the present disclosure is directed to a method forgenerating and modifying data for modules. The method may includereceiving, from a user via a proxy server, a request and userinformation associated with the user; based on the determination thatthe request comprises a test, calling a mobile application programminginterface. The mobile application programming interface may beconfigured to perform steps including retrieving data; performing thetest on the module using the retrieved data; performing a verificationon responses from the test to predetermined responses; and sendingresults of the performed verification to the user. The method mayinclude implementing the module based on the performed verification.

Yet another aspect of the present disclosure is directed to a system forgenerating and modifying data for modules. The system may include amemory storing instructions and at least one processor configured toexecute the instructions to receive, from a user via a proxy server, arequest and user information associated with the user; based on thedetermination that the request comprises a test, call a mobileapplication programming interface. The mobile application programminginterface may be configured to perform steps including retrieving data,wherein the data comprises generated simulation data including at leastone of test users, test device identifications, test platforms, testrequested information, test sample identification, or test responses;performing the test on the module using the retrieved data; performing averification on responses from the test to predetermined responses; andsending results of the performed verification to the user. The systeminstructions may include implementing the module based on the performedverification.

Other systems, methods, and computer-readable media are also discussedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations, consistent with the disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) that includes one ormore search results satisfying a search request along with interactiveuser interface elements, consistent with the disclosed embodiments.

FIG. 1C depicts a sample Single Detail Page (SDP) that includes aproduct and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 1D depicts a sample Cart page that includes items in a virtualshopping cart along with interactive user interface elements, consistentwith the disclosed embodiments.

FIG. 1E depicts a sample Order page that includes items from the virtualshopping cart along with information regarding purchase and shipping,along with interactive user interface elements, consistent with thedisclosed embodiments.

FIG. 2 is a diagrammatic illustration of an exemplary fulfillment centerconfigured to utilize disclosed computerized systems, consistent withthe disclosed embodiments.

FIG. 3 is a schematic block diagram illustrating an exemplary embodimentof a network comprising computerized systems for generating andmodifying data for module implementation, consistent with disclosedembodiments.

FIG. 4 depicts a process for generating and modifying data for moduleimplementation, consistent with disclosed embodiments.

FIG. 5 depicts a process for generating and modifying data for moduleimplementation, consistent with disclosed embodiments.

FIG. 6 depicts a sample SRP that includes an implemented module and oneor more search results satisfying a search request along withinteractive user interface elements, consistent with the disclosedembodiments.

FIG. 7 depicts a sample SDP that includes an implemented module, aproduct, and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 8 depicts a process for generating and modifying data for moduleimplementation, consistent with disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents and steps illustrated in the drawings, and the illustrativemethods described herein may be modified by substituting, reordering,removing, or adding steps to the disclosed methods. Accordingly, thefollowing detailed description is not limited to the disclosedembodiments and examples. Instead, the proper scope of the invention isdefined by the appended claims.

Embodiments of the present disclosure are directed to systems andmethods configured for generating and modifying data for modules. Thedisclosed embodiments may include users submitting a request to generateor modify data for modules via user devices. A proxy server may receivethe request and transmit the request to a request identifier of theproxy server. The request may include user information such as a moduleidentifier associated with a module and a test setting that indicateswhether the request includes a module test and the parameters (e.g.,type of test data, override settings, etc.) associated with the test.

In some embodiments, the request identifier may determine that therequest includes a test based on a loaded test setting of the request.The request identifier may determine whether the request includes arequirement that the data to be used in the test is mock data. A dataloader may call a mobile application programming interface (MAPI) basedon the determination. An internal application programming interface(API) gateway may retrieve the module associated with the request, atleast one module test (e.g., verification tests), and data (e.g.,real-time, mock, etc.) to be used on the test and send the retrievedmodule, module test, and data to at least one modular provider. Theinternal API gateway may receive the module associated with the request,module test, and data from the modular providers. The internal APIgateway may perform the module tests on the modules using the data. Themodule test may include predetermined responses such that the internalAPI gateway may perform a verification test on the modules by comparingthe module test responses of backend domains to the predeterminedresponses. For example, the implementation of a module that labels aproduct banner with a special deal for certain members may be comparedto the predetermined response that users with an identification (e.g.,user identification, device identification, etc.) associated with thespecial deal will see the special deal on the product webpage and userswithout an identification associated with the special deal will not seethe special deal on the product webpage. A backend domain may send aresponse to a user device via the proxy server, where the response mayinclude the results of the performed verification (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.) and an indication of whether the module may beimplemented.

In some embodiments, based on a determination (e.g., automatically or byusers) that the results of the performed verification meet a threshold,the tested module may be implemented by applying real-time data and themodule to at least one of the backend domains. Upon the moduleimplementation, the backend domain may send a response to the userdevice via the proxy server, where the response may include anindication that the module is implemented or analytical data associatedwith the module implementation (e.g., webpage data, webpage display,product data, seller data, user interaction with the webpage, etc.).

Referring to FIG. 1A, a schematic block diagram 100 illustrating anexemplary embodiment of a system comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations is shown. As illustrated in FIG. 1A, system 100 may include avariety of systems, each of which may be connected to one another viaone or more networks. The systems may also be connected to one anothervia a direct connection, for example, using a cable. The depictedsystems include a shipment authority technology (SAT) system 101, anexternal front end system 103, an internal front end system 105, atransportation system 107, mobile devices 107A, 1078, and 107C, sellerportal 109, shipment and order tracking (SOT) system 111, fulfillmentoptimization (FO) system 113, fulfillment messaging gateway (FMG) 115,supply chain management (SCM) system 117, warehouse management system119, mobile devices 119A, 119B, and 119C (depicted as being inside offulfillment center (FC) 200), 3^(rd) party fulfillment systems 121A,121B, and 121C, fulfillment center authorization system (FC Auth) 123,and labor management system (LMS) 125.

SAT system 101, in some embodiments, may be implemented as a computersystem that monitors order status and delivery status. For example, SATsystem 101 may determine whether an order is past its Promised DeliveryDate (PDD) and may take appropriate action, including initiating a neworder, reshipping the items in the non-delivered order, canceling thenon-delivered order, initiating contact with the ordering customer, orthe like. SAT system 101 may also monitor other data, including output(such as a number of packages shipped during a particular time period)and input (such as the number of empty cardboard boxes received for usein shipping). SAT system 101 may also act as a gateway between differentdevices in system 100, enabling communication (e.g., usingstore-and-forward or other techniques) between devices such as externalfront end system 103 and FO system 113.

External front end system 103, in some embodiments, may be implementedas a computer system that enables external users to interact with one ormore systems in system 100. For example, in embodiments where system 100enables the presentation of systems to enable users to place an orderfor an item, external front end system 103 may be implemented as a webserver that receives search requests, presents item pages, and solicitspayment information. For example, external front end system 103 may beimplemented as a computer or computers running software such as theApache HTTP Server, Microsoft Internet Information Services (IIS),NGINX, or the like. In other embodiments, external front end system 103may run custom web server software designed to receive and processrequests from external devices (e.g., mobile device 102A or computer102B), acquire information from databases and other data stores based onthose requests, and provide responses to the received requests based onacquired information.

In some embodiments, external front end system 103 may include one ormore of a web caching system, a database, a search system, or a paymentsystem. In one aspect, external front end system 103 may comprise one ormore of these systems, while in another aspect, external front endsystem 103 may comprise interfaces (e.g., server-to-server,database-to-database, or other network connections) connected to one ormore of these systems.

An illustrative set of steps, illustrated by FIGS. 1B, 1C, 1D, and 1E,will help to describe some operations of external front end system 103.External front end system 103 may receive information from systems ordevices in system 100 for presentation and/or display. For example,external front end system 103 may host or provide one or more web pages,including a Search Result Page (SRP) (e.g., FIG. 1B), a Single DetailPage (SDP) (e.g., FIG. 1C), a Cart page (e.g., FIG. 1D), or an Orderpage (e.g., FIG. 1E). A user device (e.g., using mobile device 102A orcomputer 102B) may navigate to external front end system 103 and requesta search by entering information into a search box. External front endsystem 103 may request information from one or more systems in system100. For example, external front end system 103 may request informationfrom FO System 113 that satisfies the search request. External front endsystem 103 may also request and receive (from FO System 113) a PromisedDelivery Date or “PDD” for each product included in the search results.The PDD, in some embodiments, may represent an estimate of when apackage containing the product will arrive at the user's desiredlocation or a date by which the product is promised to be delivered atthe user's desired location if ordered within a particular period oftime, for example, by the end of the day (11:59 PM). (PDD is discussedfurther below with respect to FO System 113.)

External front end system 103 may prepare an SRP (e.g., FIG. 1B) basedon the information. The SRP may include information that satisfies thesearch request. For example, this may include pictures of products thatsatisfy the search request. The SRP may also include respective pricesfor each product, or information relating to enhanced delivery optionsfor each product, PDD, weight, size, offers, discounts, or the like.External front end system 103 may send the SRP to the requesting userdevice (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clickingor tapping a user interface, or using another input device, to select aproduct represented on the SRP. The user device may formulate a requestfor information on the selected product and send it to external frontend system 103. In response, external front end system 103 may requestinformation related to the selected product. For example, theinformation may include additional information beyond that presented fora product on the respective SRP. This could include, for example, shelflife, country of origin, weight, size, number of items in package,handling instructions, or other information about the product. Theinformation could also include recommendations for similar products(based on, for example, big data and/or machine learning analysis ofcustomers who bought this product and at least one other product),answers to frequently asked questions, reviews from customers,manufacturer information, pictures, or the like.

External front end system 103 may prepare an SDP (Single Detail Page)(e.g., FIG. 1C) based on the received product information. The SDP mayalso include other interactive elements such as a “Buy Now” button, a“Add to Cart” button, a quantity field, a picture of the item, or thelike. The SDP may further include a list of sellers that offer theproduct. The list may be ordered based on the price each seller offerssuch that the seller that offers to sell the product at the lowest pricemay be listed at the top. The list may also be ordered based on theseller ranking such that the highest ranked seller may be listed at thetop. The seller ranking may be formulated based on multiple factors,including, for example, the seller's past track record of meeting apromised PDD. External front end system 103 may deliver the SDP to therequesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the productinformation. Upon receiving the SDP, the user device may then interactwith the SDP. For example, a user of the requesting user device mayclick or otherwise interact with a “Place in Cart” button on the SDP.This adds the product to a shopping cart associated with the user. Theuser device may transmit this request to add the product to the shoppingcart to external front end system 103.

External front end system 103 may generate a Cart page (e.g., FIG. 1D).The Cart page, in some embodiments, lists the products that the user hasadded to a virtual “shopping cart.” A user device may request the Cartpage by clicking on or otherwise interacting with an icon on the SRP,SDP, or other pages. The Cart page may, in some embodiments, list allproducts that the user has added to the shopping cart, as well asinformation about the products in the cart such as a quantity of eachproduct, a price for each product per item, a price for each productbased on an associated quantity, information regarding PDD, a deliverymethod, a shipping cost, user interface elements for modifying theproducts in the shopping cart (e.g., deletion or modification of aquantity), options for ordering other product or setting up periodicdelivery of products, options for setting up interest payments, userinterface elements for proceeding to purchase, or the like. A user at auser device may click on or otherwise interact with a user interfaceelement (e.g., a button that reads “Buy Now”) to initiate the purchaseof the product in the shopping cart. Upon doing so, the user device maytransmit this request to initiate the purchase to external front endsystem 103.

External front end system 103 may generate an Order page (e.g., FIG. 1E)in response to receiving the request to initiate a purchase. The Orderpage, in some embodiments, re-lists the items from the shopping cart andrequests input of payment and shipping information. For example, theOrder page may include a section requesting information about thepurchaser of the items in the shopping cart (e.g., name, address, e-mailaddress, phone number), information about the recipient (e.g., name,address, phone number, delivery information), shipping information(e.g., speed/method of delivery and/or pickup), payment information(e.g., credit card, bank transfer, check, stored credit), user interfaceelements to request a cash receipt (e.g., for tax purposes), or thelike. External front end system 103 may send the Order page to the userdevice.

The user device may enter information on the Order page and click orotherwise interact with a user interface element that sends theinformation to external front end system 103. From there, external frontend system 103 may send the information to different systems in system100 to enable the creation and processing of a new order with theproducts in the shopping cart.

In some embodiments, external front end system 103 may be furtherconfigured to enable sellers to transmit and receive informationrelating to orders.

Internal front end system 105, in some embodiments, may be implementedas a computer system that enables internal users (e.g., employees of anorganization that owns, operates, or leases system 100) to interact withone or more systems in system 100. For example, in embodiments wheresystem 100 enables the presentation of systems to enable users to placean order for an item, internal front end system 105 may be implementedas a web server that enables internal users to view diagnostic andstatistical information about orders, modify item information, or reviewstatistics relating to orders. For example, internal front end system105 may be implemented as a computer or computers running software suchas the Apache HTTP Server, Microsoft Internet Information Services(IIS), NGINX, or the like. In other embodiments, internal front endsystem 105 may run custom web server software designed to receive andprocess requests from systems or devices depicted in system 100 (as wellas other devices not depicted), acquire information from databases andother data stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, internal front end system 105 may include one ormore of a web caching system, a database, a search system, a paymentsystem, an analytics system, an order monitoring system, or the like. Inone aspect, internal front end system 105 may comprise one or more ofthese systems, while in another aspect, internal front end system 105may comprise interfaces (e.g., server-to-server, database-to-database,or other network connections) connected to one or more of these systems.

Transportation system 107, in some embodiments, may be implemented as acomputer system that enables communication between systems or devices insystem 100 and mobile devices 107A-107C. Transportation system 107, insome embodiments, may receive information from one or more mobiledevices 107A-107C (e.g., mobile phones, smart phones, PDAs, or thelike). For example, in some embodiments, mobile devices 107A-107C maycomprise devices operated by delivery workers. The delivery workers, whomay be permanent, temporary, or shift employees, may utilize mobiledevices 107A-107C to effect delivery of packages containing the productsordered by users. For example, to deliver a package, the delivery workermay receive a notification on a mobile device indicating which packageto deliver and where to deliver it. Upon arriving at the deliverylocation, the delivery worker may locate the package (e.g., in the backof a truck or in a crate of packages), scan or otherwise capture dataassociated with an identifier on the package (e.g., a barcode, an image,a text string, an RFID tag, or the like) using the mobile device, anddeliver the package (e.g., by leaving it at a front door, leaving itwith a security guard, handing it to the recipient, or the like). Insome embodiments, the delivery worker may capture photo(s) of thepackage and/or may obtain a signature using the mobile device. Themobile device may send information to transportation system 107including information about the delivery, including, for example, time,date, GPS location, photo(s), an identifier associated with the deliveryworker, an identifier associated with the mobile device, or the like.Transportation system 107 may store this information in a database (notpictured) for access by other systems in system 100. Transportationsystem 107 may, in some embodiments, use this information to prepare andsend tracking data to other systems indicating the location of aparticular package.

In some embodiments, certain users may use one kind of mobile device(e.g., permanent workers may use a specialized PDA with custom hardwaresuch as a barcode scanner, stylus, and other devices) while other usersmay use other kinds of mobile devices (e.g., temporary or shift workersmay utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user witheach device. For example, transportation system 107 may store anassociation between a user (represented by, e.g., a user identifier, anemployee identifier, or a phone number) and a mobile device (representedby, e.g., an International Mobile Equipment Identity (IMEI), anInternational Mobile Subscription Identifier (IMSI), a phone number, aUniversal Unique Identifier (UUID), or a Globally Unique Identifier(GUID)). Transportation system 107 may use this association inconjunction with data received on deliveries to analyze data stored inthe database in order to determine, among other things, a location ofthe worker, an efficiency of the worker, or a speed of the worker.

Seller portal 109, in some embodiments, may be implemented as a computersystem that enables sellers or other external entities to electronicallycommunicate with one or more systems in system 100. For example, aseller may utilize a computer system (not pictured) to upload or provideproduct information, order information, contact information, or thelike, for products that the seller wishes to sell through system 100using seller portal 109.

Shipment and order tracking system 111, in some embodiments, may beimplemented as a computer system that receives, stores, and forwardsinformation regarding the location of packages containing productsordered by customers (e.g., by a user using devices 102A-102B). In someembodiments, shipment and order tracking system 111 may request or storeinformation from web servers (not pictured) operated by shippingcompanies that deliver packages containing products ordered bycustomers.

In some embodiments, shipment and order tracking system 111 may requestand store information from systems depicted in system 100. For example,shipment and order tracking system 111 may request information fromtransportation system 107. As discussed above, transportation system 107may receive information from one or more mobile devices 107A-107C (e.g.,mobile phones, smart phones, PDAs, or the like) that are associated withone or more of a user (e.g., a delivery worker) or a vehicle (e.g., adelivery truck). In some embodiments, shipment and order tracking system111 may also request information from warehouse management system (WMS)119 to determine the location of individual products inside of afulfillment center (e.g., fulfillment center 200). Shipment and ordertracking system 111 may request data from one or more of transportationsystem 107 or WMS 119, process it, and present it to a device (e.g.,user devices 102A and 1028) upon request.

Fulfillment optimization (FO) system 113, in some embodiments, may beimplemented as a computer system that stores information for customerorders from other systems (e.g., external front end system 103 and/orshipment and order tracking system 111). FO system 113 may also storeinformation describing where particular items are held or stored. Forexample, certain items may be stored only in one fulfillment center,while certain other items may be stored in multiple fulfillment centers.In still other embodiments, certain fulfilment centers may be designedto store only a particular set of items (e.g., fresh produce or frozenproducts). FO system 113 stores this information as well as associatedinformation (e.g., quantity, size, date of receipt, expiration date,etc.).

FO system 113 may also calculate a corresponding PDD (promised deliverydate) for each product. The PDD, in some embodiments, may be based onone or more factors. For example, FO system 113 may calculate a PDD fora product based on a past demand for a product (e.g., how many timesthat product was ordered during a period of time), an expected demandfor a product (e.g., how many customers are forecast to order theproduct during an upcoming period of time), a network-wide past demandindicating how many products were ordered during a period of time, anetwork-wide expected demand indicating how many products are expectedto be ordered during an upcoming period of time, one or more counts ofthe product stored in each fulfillment center 200, which fulfillmentcenter stores each product, expected or current orders for that product,or the like.

In some embodiments, FO system 113 may determine a PDD for each producton a periodic basis (e.g., hourly) and store it in a database forretrieval or sending to other systems (e.g., external front end system103, SAT system 101, shipment and order tracking system 111). In otherembodiments, FO system 113 may receive electronic requests from one ormore systems (e.g., external front end system 103, SAT system 101,shipment and order tracking system 111) and calculate the PDD on demand.

Fulfilment messaging gateway (FMG) 115, in some embodiments, may beimplemented as a computer system that receives a request or response inone format or protocol from one or more systems in system 100, such asFO system 113, converts it to another format or protocol, and forward itin the converted format or protocol to other systems, such as WMS 119 or3^(rd) party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system 117, in some embodiments, may beimplemented as a computer system that performs forecasting functions.For example, SCM system 117 may forecast a level of demand for aparticular product based on, for example, based on a past demand forproducts, an expected demand for a product, a network-wide past demand,a network-wide expected demand, a count products stored in eachfulfillment center 200, expected or current orders for each product, orthe like. In response to this forecasted level and the amount of eachproduct across all fulfillment centers, SCM system 117 may generate oneor more purchase orders to purchase and stock a sufficient quantity tosatisfy the forecasted demand for a particular product.

Warehouse management system (WMS) 119, in some embodiments, may beimplemented as a computer system that monitors workflow. For example,WMS 119 may receive event data from individual devices (e.g., devices107A-107C or 119A-119C) indicating discrete events. For example, WMS 119may receive event data indicating the use of one of these devices toscan a package. As discussed below with respect to fulfillment center200 and FIG. 2, during the fulfillment process, a package identifier(e.g., a barcode or RFID tag data) may be scanned or read by machines atparticular stages (e.g., automated or handheld barcode scanners, RFIDreaders, high-speed cameras, devices such as tablet 119A, mobiledevice/PDA 1198, computer 119C, or the like). WMS 119 may store eachevent indicating a scan or a read of a package identifier in acorresponding database (not pictured) along with the package identifier,a time, date, location, user identifier, or other information, and mayprovide this information to other systems (e.g., shipment and ordertracking system 111).

WMS 119, in some embodiments, may store information associating one ormore devices (e.g., devices 107A-107C or 119A-119C) with one or moreusers associated with system 100. For example, in some situations, auser (such as a part- or full-time employee) may be associated with amobile device in that the user owns the mobile device (e.g., the mobiledevice is a smartphone). In other situations, a user may be associatedwith a mobile device in that the user is temporarily in custody of themobile device (e.g., the user checked the mobile device out at the startof the day, will use it during the day, and will return it at the end ofthe day).

WMS 119, in some embodiments, may maintain a work log for each userassociated with system 100. For example, WMS 119 may store informationassociated with each employee, including any assigned processes (e.g.,unloading trucks, picking items from a pick zone, rebin wall work,packing items), a user identifier, a location (e.g., a floor or zone ina fulfillment center 200), a number of units moved through the system bythe employee (e.g., number of items picked, number of items packed), anidentifier associated with a device (e.g., devices 119A-119C), or thelike. In some embodiments, WMS 119 may receive check-in and check-outinformation from a timekeeping system, such as a timekeeping systemoperated on a device 119A-119C.

3^(rd) party fulfillment (3PL) systems 121A-121C, in some embodiments,represent computer systems associated with third-party providers oflogistics and products. For example, while some products are stored infulfillment center 200 (as discussed below with respect to FIG. 2),other products may be stored off-site, may be produced on demand, or maybe otherwise unavailable for storage in fulfillment center 200. 3PLsystems 121A-121C may be configured to receive orders from FO system 113(e.g., through FMG 115) and may provide products and/or services (e.g.,delivery or installation) to customers directly. In some embodiments,one or more of 3PL systems 121A-121C may be part of system 100, while inother embodiments, one or more of 3PL systems 121A-121C may be outsideof system 100 (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) 123, in some embodiments, maybe implemented as a computer system with a variety of functions. Forexample, in some embodiments, FC Auth 123 may act as a single-sign on(SSO) service for one or more other systems in system 100. For example,FC Auth 123 may enable a user to log in via internal front end system105, determine that the user has similar privileges to access resourcesat shipment and order tracking system 111, and enable the user to accessthose privileges without requiring a second log in process. FC Auth 123,in other embodiments, may enable users (e.g., employees) to associatethemselves with a particular task. For example, some employees may nothave an electronic device (such as devices 119A-119C) and may insteadmove from task to task, and zone to zone, within a fulfillment center200, during the course of a day. FC Auth 123 may be configured to enablethose employees to indicate what task they are performing and what zonethey are in at different times of day.

Labor management system (LMS) 125, in some embodiments, may beimplemented as a computer system that stores attendance and overtimeinformation for employees (including full-time and part-time employees).For example, LMS 125 may receive information from FC Auth 123, WMS 119,devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The particular configuration depicted in FIG. 1A is an example only. Forexample, while FIG. 1A depicts FC Auth system 123 connected to FO system113, not all embodiments require this particular configuration. Indeed,in some embodiments, the systems in system 100 may be connected to oneanother through one or more public or private networks, including theInternet, an Intranet, a WAN (Wide-Area Network), a MAN(Metropolitan-Area Network), a wireless network compliant with the IEEE802.11a/b/g/n Standards, a leased line, or the like. In someembodiments, one or more of the systems in system 100 may be implementedas one or more virtual servers implemented at a data center, serverfarm, or the like.

FIG. 2 depicts a fulfillment center 200. Fulfillment center 200 is anexample of a physical location that stores items for shipping tocustomers when ordered. Fulfillment center (FC) 200 may be divided intomultiple zones, each of which are depicted in FIG. 2. These “zones,” insome embodiments, may be thought of as virtual divisions betweendifferent stages of a process of receiving items, storing the items,retrieving the items, and shipping the items. So while the “zones” aredepicted in FIG. 2, other divisions of zones are possible, and the zonesin FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound zone 203 represents an area of FC 200 where items are receivedfrom sellers who wish to sell products using system 100 from FIG. 1A.For example, a seller may deliver items 202A and 202B using truck 201.Item 202A may represent a single item large enough to occupy its ownshipping pallet, while item 202B may represent a set of items that arestacked together on the same pallet to save space.

A worker will receive the items in inbound zone 203 and may optionallycheck the items for damage and correctness using a computer system (notpictured). For example, the worker may use a computer system to comparethe quantity of items 202A and 202B to an ordered quantity of items. Ifthe quantity does not match, that worker may refuse one or more of items202A or 202B. If the quantity does match, the worker may move thoseitems (using, e.g., a dolly, a handtruck, a forklift, or manually) tobuffer zone 205. Buffer zone 205 may be a temporary storage area foritems that are not currently needed in the picking zone, for example,because there is a high enough quantity of that item in the picking zoneto satisfy forecasted demand. In some embodiments, forklifts 206 operateto move items around buffer zone 205 and between inbound zone 203 anddrop zone 207. If there is a need for items 202A or 202B in the pickingzone (e.g., because of forecasted demand), a forklift may move items202A or 202B to drop zone 207.

Drop zone 207 may be an area of FC 200 that stores items before they aremoved to picking zone 209. A worker assigned to the picking task (a“picker”) may approach items 202A and 202B in the picking zone, scan abarcode for the picking zone, and scan barcodes associated with items202A and 202B using a mobile device (e.g., device 119B). The picker maythen take the item to picking zone 209 (e.g., by placing it on a cart orcarrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored onstorage units 210. In some embodiments, storage units 210 may compriseone or more of physical shelving, bookshelves, boxes, totes,refrigerators, freezers, cold stores, or the like. In some embodiments,picking zone 209 may be organized into multiple floors. In someembodiments, workers or machines may move items into picking zone 209 inmultiple ways, including, for example, a forklift, an elevator, aconveyor belt, a cart, a handtruck, a dolly, an automated robot ordevice, or manually. For example, a picker may place items 202A and 202Bon a handtruck or cart in drop zone 207 and walk items 202A and 202B topicking zone 209.

A picker may receive an instruction to place (or “stow”) the items inparticular spots in picking zone 209, such as a particular space on astorage unit 210. For example, a picker may scan item 202A using amobile device (e.g., device 119B). The device may indicate where thepicker should stow item 202A, for example, using a system that indicatean aisle, shelf, and location. The device may then prompt the picker toscan a barcode at that location before stowing item 202A in thatlocation. The device may send (e.g., via a wireless network) data to acomputer system such as WMS 119 in FIG. 1 A indicating that item 202Ahas been stowed at the location by the user using device 1198.

Once a user places an order, a picker may receive an instruction ondevice 1198 to retrieve one or more items 208 from storage unit 210. Thepicker may retrieve item 208, scan a barcode on item 208, and place iton transport mechanism 214. While transport mechanism 214 is representedas a slide, in some embodiments, transport mechanism may be implementedas one or more of a conveyor belt, an elevator, a cart, a forklift, ahandtruck, a dolly, a cart, or the like. Item 208 may then arrive atpacking zone 211.

Packing zone 211 may be an area of FC 200 where items are received frompicking zone 209 and packed into boxes or bags for eventual shipping tocustomers. In packing zone 211, a worker assigned to receiving items (a“rebin worker”) will receive item 208 from picking zone 209 anddetermine what order it corresponds to. For example, the rebin workermay use a device, such as computer 119C, to scan a barcode on item 208.Computer 119C may indicate visually which order item 208 is associatedwith. This may include, for example, a space or “cell” on a wall 216that corresponds to an order. Once the order is complete (e.g., becausethe cell contains all items for the order), the rebin worker mayindicate to a packing worker (or “packer”) that the order is complete.The packer may retrieve the items from the cell and place them in a boxor bag for shipping. The packer may then send the box or bag to a hubzone 213, e.g., via forklift, cart, dolly, handtruck, conveyor belt,manually, or otherwise.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags(“packages”) from packing zone 211. Workers and/or machines in hub zone213 may retrieve package 218 and determine which portion of a deliveryarea each package is intended to go to, and route the package to anappropriate camp zone 215. For example, if the delivery area has twosmaller sub-areas, packages will go to one of two camp zones 215. Insome embodiments, a worker or machine may scan a package (e.g., usingone of devices 119A-119C) to determine its eventual destination. Routingthe package to camp zone 215 may comprise, for example, determining aportion of a geographical area that the package is destined for (e.g.,based on a postal code) and determining a camp zone 215 associated withthe portion of the geographical area.

Camp zone 215, in some embodiments, may comprise one or more buildings,one or more physical spaces, or one or more areas, where packages arereceived from hub zone 213 for sorting into routes and/or sub-routes. Insome embodiments, camp zone 215 is physically separate from FC 200 whilein other embodiments camp zone 215 may form a part of FC 200.

Workers and/or machines in camp zone 215 may determine which routeand/or sub-route a package 220 should be associated with, for example,based on a comparison of the destination to an existing route and/orsub-route, a calculation of workload for each route and/or sub-route,the time of day, a shipping method, the cost to ship the package 220, aPDD associated with the items in package 220, or the like. In someembodiments, a worker or machine may scan a package (e.g., using one ofdevices 119A-119C) to determine its eventual destination. Once package220 is assigned to a particular route and/or sub-route, a worker and/ormachine may move package 220 to be shipped. In exemplary FIG. 2, campzone 215 includes a truck 222, a car 226, and delivery workers 224A and224B. In some embodiments, truck 222 may be driven by delivery worker224A, where delivery worker 224A is a full-time employee that deliverspackages for FC 200 and truck 222 is owned, leased, or operated by thesame company that owns, leases, or operates FC 200. In some embodiments,car 226 may be driven by delivery worker 224B, where delivery worker224B is a “flex” or occasional worker that is delivering on an as-neededbasis (e.g., seasonally). Car 226 may be owned, leased, or operated bydelivery worker 224B.

Referring to FIG. 3, a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems for generatingand modifying data for module implementation, consistent with disclosedembodiments is shown. As illustrated in FIG. 3, a system 300 may includea user device 301, a proxy server 310, a mobile application programminginterface (MAPI) 315, an internal fluent application programminginterface (API) gateway 316, system 320, system 330, and system 340,each of which may communicate with each other via a network. In someembodiments, the systems and components of system 300 may communicatewith the other components of system 300 via a direct connection, forexample, using a cable. In some other embodiments, system 300 may be apart of system 100 of FIG. 1A and may communicate with the othercomponents of system 100 via a network or via a direct connection, forexample, using a cable. The systems and components of system 300 mayeach comprise a single computer or may each be configured as adistributed computer system including multiple computers thatinteroperate to perform one or more of the processes and functionalitiesassociated with the disclosed examples.

Proxy server 310 may include a proxy controller 311 and a proxy serviceincluding a request identifier 312, a pre-processor 313, a data loader314, and a post processor 315. System 320 may include a modular frontplatform API 321, which may include a page layout service and a moduletest service. System 320 may include a modular front platformadministrator 322, which may include a page layout manager, a moduletest manager, a module manager, and a provider manager. System 320 mayinclude a database 323. System 330 may include at least one modularprovider, such as modular providers 331-333 (e.g., modular providers A,B, C, etc.), where each modular provider may include at least onemodule. System 340 may include at least one internal API gateway 341 andat least one respective backend domain 342.

System 300 may comprise processors, memories, and databases. Theprocessors may be one or more known processing devices, such as amicroprocessor from the Pentium™ family manufactured by Intel™ or theTurion™ family manufactured by AMD™. The processors may constitute asingle core or multiple core processor that executes parallel processessimultaneously. For example, the processors may use logical processorsto simultaneously execute and control multiple processes. The processorsmay implement virtual machine technologies or other known technologiesto provide the ability to execute, control, run, manipulate, store, etc.multiple software processes, applications, programs, etc. In anotherexample, the processors may include a multiple-core processorarrangement configured to provide parallel processing functionalities toallow system 300 to execute multiple processes simultaneously. One ofordinary skill in the art would understand that other types of processorarrangements could be implemented that provide for the capabilitiesdisclosed herein.

The memories may store one or more operating systems that perform knownoperating system functions when executed by the processors,respectively. By way of example, the operating system may includeMicrosoft Windows, Unix, Linux, Android, Mac OS, iOS, or other types ofoperating systems. Accordingly, examples of the disclosed invention mayoperate and function with computer systems running any type of operatingsystem. The memories may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible computer readable medium.

The databases (e.g., database 323) may include, for example, Oracle™databases, Sybase™ databases, or other relational databases ornon-relational databases, such as Hadoop™ sequence files, HBase™, orCassandra™. The databases may include computing components (e.g.,database management system, database server, etc.) configured to receiveand process requests for data stored in memory devices of thedatabase(s) and to provide data from the database(s). The databases mayinclude NoSQL databases such as HBase, MongoDB™ or Cassandra™.Alternatively, the databases may include relational databases such asOracle, MySQL and Microsoft SQL Server. In some embodiments, thedatabases may take the form of servers, general purpose computers,mainframe computers, or any combination of these components.

The databases may store data that may be used by the processors forperforming methods and processes associated with disclosed examples. Thedatabases may be located in the systems or components of system 300 or,alternatively, they may be in external storage devices located outsideof the systems or components of system 300. Data stored in the databasesmay include any suitable data associated with users or modules (e.g.,test data, real-time data, module data, test results, real-time userinteractions with online platform, test user interactions with onlineplatform, etc.).

User device 301 may be a tablet, mobile device, computer, or the like.User device 301 may include a display. The display may include, forexample, liquid crystal displays (LCD), light emitting diode screens(LED), organic light emitting diode screens (OLED), a touch screen, andother known display devices. The display may show various information toa user. For example, it may display a webpage (e.g., FIGS. 1B-1E) thatincludes an implemented module or an option to test a module. Userdevice 301 may include one or more input/output (I/O) devices. The I/Odevices may include one or more devices that allow user device 301 tosend and receive information from user device 301 or another device. TheI/O devices may include various input/output devices, a camera, amicrophone, a keyboard, a mouse-type device, a gesture sensor, an actionsensor, a physical button, an oratory input, etc. The I/O devices mayalso include one or more communication modules (not shown) for sendingand receiving information from proxy server 310 by, for example,establishing wired or wireless connectivity between user device 301 andproxy server 310.

In some embodiments, the users associated with user device 301 may beinternal users (e.g., employees of an organization that develops, owns,operates, or leases systems 100 or 300). Internal front end system 105may be implemented as a computer system that enables the usersassociated with user device 301 to interact with system 300. Forexample, in some embodiments, internal front end system 105 may beimplemented as a web server that enables the users associated with userdevice 301 to modify modules, add new modules, submit requests to test(e.g., perform verifications on) modules, submit requests to implementmodules (e.g., modules may be implemented by inserting the module into awebpage), to view diagnostic and statistical information about tested orimplemented modules, etc. In some embodiments, internal front end system105 may run custom web server software designed to receive and processrequests from systems or devices depicted in systems 100 or 300, acquireinformation from databases (e.g., database 323) and other data storesbased on those requests, and provide responses to the received requestsbased on acquired information.

Modular front platform API 321 of system 320 may create, read, or modifydata such as test data or modules (e.g., users may generate, modify, orsubmit test data or modules to system 300 via modular front platform API321). Modular front platform administrator 322 may manage servicesrequired to fulfill calls to modular front platform API 321 receivedfrom internal API gateway 316 and to return appropriate responses tointernal (fluent) API gateway 316 (e.g., modular front platform API 321may appropriately return test data to internal API gateway 316 wheninternal API gateway 316 calls for a test). Database 323 may store datafrom system 300, such as generated, modified, or submitted test data ormodules. Internal API gateway 316 may be fluent, advantageouslyproviding an easily readable (e.g., code that can be read as humanlanguage), flowing interface gateway that may mimic a domain specificlanguage. Fluent API gateways may increase the efficiency of methodsperformed in system 300 by providing a context for further actions foreach method performed.

Modules may include labeling a product banner or header of a product ona webpage, where the product banner may indicate a discounted product, aproduct promotion (e.g., a product promotion associated with a season orholiday), or a special deal for certain users (e.g., certain users maybe considered “high-value” if they are frequent customers, hold aspecial membership, etc.).

Internal API gateway 341 of system 340 may receive modules associatedand data (e.g., test data or real-time data) from modular providers331-333. In some embodiments, modular providers 331-333 may be usedbased on the type of data to be used during testing. For example,modular providers 331 and 332 may be “local” modular providers that usetest data (e.g., mock data) while modular provider 333 may be a“production” modular provider that uses real-time data (e.g., data fromactual production). Internal API gateway 341 may implement modules byinserting the modules into at least one webpage of backend domains 342of system 340. Upon the module implementation, backend domain 342 maysend responses to user device 301 via proxy server 310.

Referring to FIG. 4, a process 400 for generating and modifying data formodule implementation, consistent with disclosed embodiments is shown.

At step 401, user device 301 may submit a request to generate or modifydata for modules. Proxy server 310 may receive the request via proxycontroller 311, which may transmit the request to request identifier312. The request may include a module identifier associated with amodule and a test setting that indicates whether the request includes amodule test and the parameters (e.g., type of test data, overridesettings, etc.) associated with the test. At step 402, requestidentifier 312 may load the test setting of the request.

At step 403, request identifier 312 may determine whether the requestincludes a module test based on the loaded test setting of the request.Request identifier 312 may determine that the request does not include atest and at step 420, call MAPI 317 based on the determination. Based onthe call to MAPI 317, internal API gateway 316 may retrieve the moduleassociated with the request and real-time data from system 320 and sendthe retrieved module and real-time data to at least one of modularproviders 331-333. Internal API gateway 341 may receive the moduleassociated with the request and real-time data from modular providers331-333 of system 330. Based on the determination that the request doesnot include a test, internal API gateway 341 may implement the moduleassociated with the request by inserting the module into at least onewebpage of backend domains 342 of system 340. Upon the moduleimplementation, backend domain 342 may send a response to user device301 via proxy server 310, where the response may include an indicationthat the module is implemented or analytical data associated with themodule implementation (e.g., webpage data, webpage display, productdata, seller data, user interaction with the webpage, etc.).

Going back to step 403, request identifier 312 may determine that therequest includes a test based on the loaded test setting of the request.At step 405, request identifier 312 may determine whether the requestincludes a requirement that the data to be used in the test is mockdata. Request identifier 312 may determine that the request does notinclude a requirement that the test use mock data. At step 406,pre-processor 313 may request an override for real-time test data and atstep 407, data loader 314 may call MAPI 317 based on the determination.

At step 408, post processor 315 may determine whether the requestincludes an override setting. Based on a determination that the requestdoes not include an override setting and based on the call to MAPI 317,internal API gateway 316 may retrieve the module associated with therequest, at least one module test (e.g., verification tests), andreal-time data to be used on the test from system 320 and send theretrieved module, module test, and real-time data to at least one ofmodular providers 331-333. Internal API gateway 341 may receive themodule associated with the request, module test, and real-time data frommodular providers 331-333 of system 330. Internal API gateway 341 mayperform the module tests on the modules using the real-time data,thereby allowing the modules to be tested in realistic scenarios (e.g.,real-time data may be used to replicate or simulate real userinteractions with the tested module). Real-time data may include useridentifications, device identifications, etc. The module test mayinclude predetermined responses such that internal API gateway 341 mayperform a verification test on the modules by comparing the module testresponses of backend domains 342 to the predetermined responses. Forexample, the implementation of a module that labels a product bannerwith a special deal for certain members may be compared to thepredetermined response that users with an identification (e.g., useridentification, device identification, etc.) associated with the specialdeal will see the special deal on the product webpage and users withoutan identification associated with the special deal will not see thespecial deal on the product webpage.

At step 409, backend domain 342 may send a response to user device 301via proxy server 310, where the response may include the results of theperformed verification (e.g., webpage data, webpage display, productdata, seller data, user interaction with the webpage, etc.) and anindication of whether the module may be implemented.

Based on a determination (e.g., automatically by system 300 or by users)that the results of the performed verification meet a threshold, thetested module may be implemented by applying inserting the module intoat least one webpage of backend domains 342 of system 340. Upon themodule implementation, backend domain 342 may send a response to userdevice 301 via proxy server 310, where the response may include anindication that the module is implemented or analytical data associatedwith the module implementation (e.g., webpage data, webpage display,product data, seller data, user interaction with the webpage, etc.).Based on a determination that the results of the performed verificationdo not meet the threshold, the tested module may be further developed(e.g., modified) before it is implemented.

Going back to step 408, post processor 315 may determine that therequest includes an override setting. If the request includes anoverride value that meets the threshold of the override setting, theninternal API gateway 341 may implement the module, in a manner describedpreviously, without performing a module test. For example, an overridesetting may allow tests to be bypassed or mock data to be applied basedon an override value. The override value may include clientidentifications, path or query conditions, time period, user memberstatus, age of the module (e.g., time the module was created orsubmitted), etc.

At step 409 upon the module implementation, backend domain 342 may senda response to user device 301 via proxy server 310, where the responsemay include an indication that the module is implemented or analyticaldata associated with the module implementation (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.).

Going back to step 405, request identifier 312 may determine that therequest includes a requirement that the test use mock data. At step 410,data loader 314 may call MAPI 317 and return mock data for the testbased on the determination.

At step 408, post processor 315 may determine whether the requestincludes an override setting. Based on a determination that the requestdoes not include an override setting and based on the call to MAPI 317,internal API gateway 316 may retrieve the module associated with therequest, at least one module test (e.g., verification tests), and mockdata to be used on the test from system 320 and send the retrievedmodule, module test, and mock data to at least one of modular providers331-333. Internal API gateway 341 may receive the module associated withthe request, module test, and mock data from modular providers 331-333of system 330. Internal API gateway 341 may perform the module tests onthe modules using the mock data. Mock data and module tests may includeuser-generated or computer-generated user identifications, deviceidentifications, descriptions, mock test set identifications, test unitidentifications, target methods, target request paths, target requestqueries, target request hosts, target request bodies, platforms,responses, preprocesses, postprocesses, mock test request forgeryidentifications, actions, action keys, action values, date and time,test samples, products, filters, filter keys, product categories, etc.The module test may include predetermined responses such that internalAPI gateway 341 may perform a verification test on the modules bycomparing the module test responses of backend domains 342 to thepredetermined responses. Backend domain 342 may send a response to userdevice 301 via proxy server 310, where the response may include theresults of the performed verification (e.g., webpage data, webpagedisplay, product data, seller data, user interaction with the webpage,etc.) and an indication of whether the module may be implemented. Basedon a determination (e.g., automatically by system 300 or by users) thatthe results of the performed verification meet a threshold, the testedmodule may be implemented by inserting the module into at least onewebpage of backend domains 342 of system 340.

At step 409 upon the module implementation, backend domain 342 may senda response to user device 301 via proxy server 310, where the responsemay include an indication that the module is implemented or analyticaldata associated with the module implementation (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.). Based on a determination that the results of theperformed verification do not meet the threshold, the tested module maybe further developed (e.g., modified) before it is implemented.

Going back to step 408, post processor 315 may determine that therequest includes an override setting. If the request includes anoverride value that meets the threshold of the override setting, theninternal API gateway 341 may implement the module, in a manner describedpreviously, without performing a module test.

At step 409 upon the module implementation, backend domain 342 may senda response to user device 301 via proxy server 310, where the responsemay include an indication that the module is implemented or analyticaldata associated with the module implementation (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.).

Referring to FIG. 5, a process 500 for generating and modifying data formodule implementation, consistent with disclosed embodiments is shown.

At step 501, a user may submit a request to generate or modify data formodules via user device 301 in a manner similar to step 401 of process400. The request may include sample data that may be used in a moduletest. For example, proxy server 310 may receive the request via proxycontroller 311, which may transmit the request to request identifier312. The request may include a module identifier associated with amodule and a test setting that indicates whether the request includes amodule test and the parameters (e.g., type of test data, overridesettings, etc.) associated with the test.

At step 502, request identifier 312 may load the test setting of therequest. Request identifier 312 may determine whether the requestincludes a module test based on the loaded test setting of the request.Request identifier 312 may determine that the request includes a testbased on the loaded test setting of the request. Request identifier 312may determine whether the request includes a requirement that the data(e.g., the sample data) to be used in the test is mock data. Requestidentifier 312 may determine that the request does not include arequirement that the test use mock data. At step 503, pre-processor 313may request an override for real-time test data and at step 504, dataloader 314 may call MAPI 317 based on the determination.

At step 505, data loader 314 may determine whether the submitted sampledata is duplicate data by calling MAPI 317 to determine whether database323 includes the submitted sample data. MAPI 317 may send a response todata loader 314 that indicates that the submitted sample data is notduplicate data. At step 506 upon receiving the response, data loader 313may insert the new sample data as test data and process 500 may proceedto step 509 in a manner similar to process 400. If MAPI 317 sends aresponse to data loader 314 that indicates that the submitted sampledata is duplicate data, then process 500 may proceed to step 507.

At step 509, post processor 315 may determine whether the requestincludes an override setting. Based on a determination that the requestdoes not include an override setting and based on the call to MAPI 317,internal API gateway 316 may retrieve the module associated with therequest, at least one module test (e.g., verification tests), andreal-time data to be used on the test from system 320 and send theretrieved module, module test, and real-time data to at least one ofmodular providers 331-333. Internal API gateway 341 may receive themodule associated with the request, module test, and real-time data frommodular providers 331-333 of system 330. Internal API gateway 341 mayperform the module tests on the modules using the real-time data,thereby allowing the modules to be tested in realistic scenarios (e.g.,real-time data may be used to replicate or simulate real userinteractions with the tested module). Real-time data may include useridentifications, device identifications, etc. The module test mayinclude predetermined responses such that internal API gateway 341 mayperform a verification test on the modules by comparing the module testresponses of backend domains 342 to the predetermined responses. Forexample, the implementation of a module that labels a product bannerwith a special deal for certain members may be compared to thepredetermined response that users with an identification (e.g., useridentification, device identification, etc.) associated with the specialdeal will see the special deal on the product webpage and users withoutan identification associated with the special deal will not see thespecial deal on the product webpage.

At step 510, backend domain 342 may send a response to user device 301via proxy server 310, where the response may include the results of theperformed verification (e.g., webpage data, webpage display, productdata, seller data, user interaction with the webpage, etc.) and anindication of whether the module may be implemented.

Based on a determination (e.g., automatically by system 300 or by users)that the results of the performed verification meet a threshold, thetested module may be implemented by applying inserting the module intoat least one webpage of backend domains 342 of system 340. Upon themodule implementation, backend domain 342 may send a response to userdevice 301 via proxy server 310, where the response may include anindication that the module is implemented or analytical data associatedwith the module implementation (e.g., webpage data, webpage display,product data, seller data, user interaction with the webpage, etc.).Based on a determination that the results of the performed verificationdo not meet the threshold, the tested module may be further developed(e.g., modified) before it is implemented.

Going back to step 509, post processor 315 may determine that therequest includes an override setting. If the request includes anoverride value that meets the threshold of the override setting, theninternal API gateway 341 may implement the module, in a manner describedpreviously, without performing a module test. For example, an overridesetting may allow tests to be bypassed or mock data to be applied basedon an override value. The override value may include clientidentifications, path or query conditions, time period, user memberstatus, age of the module (e.g., time the module was created orsubmitted), etc.

At step 510 upon the module implementation, backend domain 342 may senda response to user device 301 via proxy server 310, where the responsemay include an indication that the module is implemented or analyticaldata associated with the module implementation (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.).

At step 507, data loader 314 may determine whether the duplicate sampledata has been stored in database 323 for more than twenty-four hours bycalling MAPI 317. MAPI 317 may send a response to data loader 314 thatindicates that the duplicate sample data has not been stored in database323 for more than twenty-four hours. Upon receiving the response, dataloader 314 may not insert the submitted duplicate sample data andprocess 500 may proceed to steps 509 and 510 as described above. If MAPI317 sends a response to data loader 314 that indicates that theduplicate sample data has been stored in database 323 for more thantwenty-four hours, then at step 508, data loader 314 may update thesample data with the submitted sample data, where the submitted sampledata may be inserted as test data. Process 500 may proceed to steps 509and 510 as described above.

Going back to step 502, request identifier 312 may determine that therequest includes a requirement that the test use mock data. Data loader314 may call MAPI 317 and return mock data for the test based on thedetermination and proceeds to steps 509 and 510 as described above.

Referring to FIG. 6, a sample SRP 600 that includes an implementedmodule 601 and one or more search results 603 satisfying a searchrequest along with interactive user interface elements, consistent withthe disclosed embodiments is shown. For example, the implemented module601 may include labeling a product banner or header of a product on awebpage, where the product banner may indicate a special deal forcertain users (e.g., certain users may be considered “high-value” ifthey are frequent customers, hold a special membership, etc.). Forexample, sample SRP 600 may display search results 603 of a high-valueuser, where search results 603 include an expedited delivery of productsto the high-value user.

Referring to FIG. 7, a sample SDP 700 that includes an implementedmodule 701, a product 703, and information about the product along withinteractive user interface elements, consistent with the disclosedembodiments is shown. For example, implemented module 701 may includelabeling a product banner or header of a product on a webpage, where theproduct banner may indicate a special deal for certain users (e.g.,certain users may be considered “high-value” if they are frequentcustomers, hold a special membership, etc.). For example, sample SDP 700may display free and expedited shipping of products to the high-valueuser.

Referring to FIG. 8, a process 800 for generating and modifying data formodule implementation, consistent with disclosed embodiments is shown.

At step 801, a user may submit a request to generate or modify data formodules via user device 301. Proxy server 310 may receive the requestvia proxy controller 311, which may transmit the request to requestidentifier 312. The request may include user information such as amodule identifier associated with a module and a test setting thatindicates whether the request includes a module test and the parameters(e.g., type of test data, override settings, etc.) associated with thetest. Request identifier 312 may load the test setting of the request.

At step 803, request identifier 312 may determine that the requestincludes a test based on the loaded test setting of the request. Requestidentifier 312 may determine whether the request includes a requirementthat the data to be used in the test is mock data. Data loader 314 maycall MAPI 317 based on the determination. Internal API gateway 316 mayretrieve the module associated with the request, at least one moduletest (e.g., verification tests), and data (e.g., real-time, mock, etc.)to be used on the test from system 320 and send the retrieved module,module test, and data to at least one of modular providers 331-333.Internal API gateway 341 may receive the module associated with therequest, module test, and data from modular providers 331-333 of system330. Internal API gateway 341 may perform the module tests on themodules using the data. The module test may include predeterminedresponses such that internal API gateway 341 may perform a verificationtest on the modules by comparing the module test responses of backenddomains 342 to the predetermined responses. For example, theimplementation of a module that labels a product banner with a specialdeal for certain members may be compared to the predetermined responsethat users with an identification (e.g., user identification, deviceidentification, etc.) associated with the special deal will see thespecial deal on the product webpage and users without an identificationassociated with the special deal will not see the special deal on theproduct webpage. Backend domain 342 may send a response to user device301 via proxy server 310, where the response may include the results ofthe performed verification (e.g., webpage data, webpage display, productdata, seller data, user interaction with the webpage, etc.) and anindication of whether the module may be implemented.

At step 805, based on a determination (e.g., automatically by system 300or by users) that the results of the performed verification meet athreshold, the tested module may be implemented by applying thereal-time data and the module to at least one of backend domains 342 ofsystem 340. Upon the module implementation, backend domain 342 may senda response to user device 301 via proxy server 310, where the responsemay include an indication that the module is implemented or analyticaldata associated with the module implementation (e.g., webpage data,webpage display, product data, seller data, user interaction with thewebpage, etc.).

While the present disclosure has been shown and described with referenceto particular embodiments thereof, it will be understood that thepresent disclosure can be practiced, without modification, in otherenvironments. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. Additionally,although aspects of the disclosed embodiments are described as beingstored in memory, one skilled in the art will appreciate that theseaspects can also be stored on other types of computer readable media,such as secondary storage devices, for example, hard disks or CD ROM, orother forms of RAM or ROM, USB media, DVD, Blu-ray, or other opticaldrive media.

Computer programs based on the written description and disclosed methodsare within the skill of an experienced developer. Various programs orprogram modules can be created using any of the techniques known to oneskilled in the art or can be designed in connection with existingsoftware. For example, program sections or program modules can bedesigned in or by means of .Net Framework, .Net Compact Framework (andrelated languages, such as Visual Basic, C, etc.), Java, C++,Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with includedJava applets.

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

1-20. (canceled)
 21. A computer-implemented system for generating andmodifying data for modules, comprising: a memory storing instructions;and at least one processor configured to execute the instructions to:based on a determination that a received request comprises a test, callan application programming interface, wherein the applicationprogramming interface is configured to perform steps comprising:performing the test on the module using retrieved data; performing averification on responses from the test; and sending results of theperformed verification to the user; based on the performed verification,implement the module.
 22. The system of claim 21, wherein based on adetermination that the received request does not comprise a test, theinstructions comprise: calling the application programming interface;and implementing the module.
 23. The system of claim 21, wherein thereceived request comprises a requirement that the retrieved datacomprises mock data.
 24. The system of claim 23, wherein the stepsfurther comprise: determining that the test comprises an overridesetting; determining that the received request comprises an overridevalue associated with the override setting; and based on thedetermination that the received request comprises the override valueassociated with the override setting, implementing the module withoutperforming the test.
 25. The system of claim 23, wherein the stepsfurther comprise: determining that the test comprises an overridesetting; determining that the received request does not comprise anoverride value associated with the override setting; and implementingthe module based on the performed verification.
 26. The system of claim23, wherein the steps further comprise: determining that the test doesnot comprise an override setting; and implementing the module based onthe performed verification.
 27. The system of claim 21, wherein thereceived request comprises a requirement that the retrieved datacomprises real data.
 28. The system of claim 27, wherein theinstructions further comprise: requesting an override action based on adetermination that the test does not require mock data; calling theapplication programming interface; determining that the test comprisesan override setting; determining that the received request comprises anoverride value associated with the override setting; and implementingthe module without performing the test based on the determination thatthe received request comprises the override value associated with theoverride setting.
 29. The system of claim 27, wherein the instructionsfurther comprise: requesting an override action based on a determinationthat the test does not require mock data; calling the applicationprogramming interface; determining that the test comprises an overridesetting; determining that the received request does not comprise anoverride value associated with the override setting; and implementingthe module based on the performed verification.
 30. The system of claim27, wherein the instructions further comprise: requesting an overrideaction based on a determination that the test does not require mockdata; calling the application programming interface; determining thatthe test does not comprise an override setting; and implementing themodule based on the performed verification.
 31. A computer-implementedmethod for generating and modifying data for modules, comprising: basedon a determination that a received request comprises a test, calling anapplication programming interface, wherein the application programminginterface is configured to perform steps comprising: performing the teston the module using retrieved data; performing a verification onresponses from the test; and sending results of the performedverification to the user; based on the performed verification,implementing the module.
 32. The method of claim 31, further comprising:based on a determination that the received request does not comprise atest: calling the application programming interface; and implementingthe module.
 33. The method of claim 31, wherein the received requestcomprises a requirement that the retrieved data comprises mock data. 34.The method of claim 33, wherein the steps further comprise: determiningthat the test comprises an override setting; determining that thereceived request comprises an override value associated with theoverride setting; and based on the determination that the receivedrequest comprises the override value associated with the overridesetting, implementing the module without performing the test.
 35. Themethod of claim 33, wherein the steps further comprise: determining thatthe test comprises an override setting; determining that the receivedrequest does not comprise an override value associated with the overridesetting; and implementing the module based on the performedverification.
 36. The method of claim 33, wherein the steps furthercomprise: determining that the test does not comprise an overridesetting; and implementing the module based on the performedverification.
 37. The system of claim 31, wherein the received requestcomprises a requirement that the retrieved data comprises real data. 38.The method of claim 31, further comprising: requesting an overrideaction based on a determination that the test does not require mockdata; calling the application programming interface; determining thatthe test comprises an override setting; determining that the receivedrequest comprises an override value associated with the overridesetting; and implementing the module without performing the test basedon the determination that the received request comprises the overridevalue associated with the override setting.
 39. The method of claim 31,further comprising: requesting an override action based on adetermination that the test does not require mock data; calling theapplication programming interface; determining that the test comprisesan override setting; determining that the received request does notcomprise an override value associated with the override setting; andimplementing the module based on the performed verification.
 40. Themethod of claim 37, further comprising: requesting an override actionbased on a determination that the test does not require mock data;calling the application programming interface; determining that the testdoes not comprise an override setting; and implementing the module basedon the performed verification.